xen: Fix XenStore initialisation for XS_LOCAL
authorDavid Woodhouse <dwmw@amazon.co.uk>
Tue, 26 Jan 2021 17:01:49 +0000 (17:01 +0000)
committerSalvatore Bonaccorso <carnil@debian.org>
Sat, 30 Jan 2021 20:38:57 +0000 (20:38 +0000)
commit3d08d6e5c5eaab10f06a72354d8878dd784d3fb0
tree7f82335bfe593a62da2a499dd3f400c8c1187fc4
parentdd06bba832a39222d43c539e258906a8d9cc811c
xen: Fix XenStore initialisation for XS_LOCAL

Origin: https://git.kernel.org/linus/5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1

In commit 3499ba8198ca ("xen: Fix event channel callback via INTX/GSI")
I reworked the triggering of xenbus_probe().

I tried to simplify things by taking out the workqueue based startup
triggered from wake_waiting(); the somewhat poorly named xenbus IRQ
handler.

I missed the fact that in the XS_LOCAL case (Dom0 starting its own
xenstored or xenstore-stubdom, which happens after the kernel is booted
completely), that IRQ-based trigger is still actually needed.

So... put it back, except more cleanly. By just spawning a xenbus_probe
thread which waits on xb_waitq and runs the probe the first time it
gets woken, just as the workqueue-based hack did.

This is actually a nicer approach for *all* the back ends with different
interrupt methods, and we can switch them all over to that without the
complex conditions for when to trigger it. But not in -rc6. This is
the minimal fix for the regression, although it's a step in the right
direction instead of doing a partial revert and actually putting the
workqueue back. It's also simpler than the workqueue.

Fixes: 3499ba8198ca ("xen: Fix event channel callback via INTX/GSI")
Reported-by: Juergen Gross <jgross@suse.com>
Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
Reviewed-by: Juergen Gross <jgross@suse.com>
Link: https://lore.kernel.org/r/4c9af052a6e0f6485d1de43f2c38b1461996db99.camel@infradead.org
Signed-off-by: Juergen Gross <jgross@suse.com>
Gbp-Pq: Topic bugfix/all
Gbp-Pq: Name xen-Fix-XenStore-initialisation-for-XS_LOCAL.patch
drivers/xen/xenbus/xenbus_probe.c